<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
   "http://www.w3.org/TR/html4/loose.dtd">

<html lang="en">
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
	<title>Scheduler - Chemistry Interview</title>
	<meta name="generator" content="TextMate http://macromates.com/">
	<meta name="author" content="Nate Chamness">
	<!-- Date: 2011-10-18 -->
</head>
<body>
Mike Soldner and Nathaniel Chamness
<p>
Professor Kingsbury
</p>

<p>
	1. He is the only one that does scheduling in the department. Gets some help from the office. Gets constraints from the teachers/head office. Sets up an Excel file, begins scheduling and then runs it by the faculty. Multiple iterations happen. Takes forever.
</p>

<p>
	2. Through e-mail.
</p>

<p>
	3.
	Views that allow him to see what other departments are doing. Typical classes between two departments shouldn't be scheduled at the same time.
	Drag and drop (game-like)
	Multiple views get updated when any one of the gets new data.
	Conflicts notify the users as soon as they occur.
	Enrollment information that dynamically updates. Who is trying to take what classes. Who still needs to take the classes still.
</p>

<p>
	4.
	Benefits: Saves time
	Gives students the classes they need.
	Negatives: Learning curve
</p>

<p>
	5.
	Descriptive Conflicts.
	Some way to give criticism for the teachers.
	Previous schedules and easily accessible.
	Subgroups. Can take multiple schedules and merge them together. If PChem and OChem make schedules, he can merge them together.
	Instructor information easily available.
	Everything highly dynamic.
</p>

</body>
</html>
